Installation as Windows Service

To install Orchestra Solution Hub as a service in Windows follow these steps:

To run as a Windows service, Orchestra Solution Hub uses the Apache commons daemon, which is capable of running Java applications as a Windows service. Please refer to the Apache documentation for details on this daemon.

The service can be installed and uninstalled using the following scripts located in the startscripts\WindowsService folder:

• service_installer_32bit.cmd for Service on 32-bit environments
• service_installer_64bit.cmd for Service on 64-bit environments

info

Depending on your windows installation please use the 32bit or 64bit executable. Please open a command line with "run as administrator" since administrator privileges are required for a service installation.

Available commands:

• Install a service: service_installer_<bit>.cmd install
• Uninstall the service: service_installer_<bit>.cmd uninstall
• Update the service: service_installer_<bit>.cmd update

---

Configuration of Derby-Logging

Logging from the Derby database can also be customized. To configure the Derby properties, edit the file:

<installation dir>/startscripts/WindowsService/derby.properties

Because Solution Hub is installed as a service, we need to pass the home path of derby.
This is done by editing the file service_installer_<bit>.cmd and passing the -D Java argument in the JAVA_OPTS variable:

-Dderby.system.home=<installation dir>/startscripts/WindowsService

The following properties are already configured:

Name	Default	Description
derby.stream.error.style	rollingFile	If you set this property to rollingFile (the only supported value), Derby by default creates up to 10 rolling files named derby-0.log, derby-1.log, and so on, up to derby-9.log, each with a maximum length of 1,024,000 bytes. You can override any of these defaults by setting one or more of the following properties.
derby.stream.error.rollingFile.limit	8,388,608 (Bytes)	The derby.stream.error.rollingFile.limit property specifies the number of bytes to which to limit each rolling log file before it is rolled over to the next file, if derby.stream.error.style is set to rollingFile.
derby.stream.error.rollingFile.count	10	The derby.stream.error.rollingFile.count property specifies the number of rolling log files to permit before deleting the oldest file when rolling to the next file, if derby.stream.error.style is set to rollingFile.

info

• For the changes to take effect, you must restart the service.
• You can restore the default Derby settings by removing the derby.properties file.
• Additional parameters can be found in the Derby documentation (apache.org).